Systems Design: Simulating the SDLC with GOAP
Introduction: The work here aims to show the use of the algorithm "Goal Oriented Action Planning" (GOAP) on a simulated Software Development Life Cycle (SDLC) process.
Workflow Steps
1. Customer arrives to be collected and interviewed by Req Manager. Req Delivered is incremented by 1.
2. Lead takes reqs and builds out tasks (in task room). Tasks are inc by 1
3. Developer chooses a task and works to implement it. Implemented is inc by 1
4. Tester tests implemented result to confirm the result is in line with the requirement definition. Delivered is inc by 1.
This is an example of an infinite game.
1. Customer arrives to be collected and interviewed by Req Manager. Req Delivered is incremented by 1.
2. Lead takes reqs and builds out tasks (in task room). Tasks are inc by 1
3. Developer chooses a task and works to implement it. Implemented is inc by 1
4. Tester tests implemented result to confirm the result is in line with the requirement definition. Delivered is inc by 1.
This is an example of an infinite game.
The following explains the on-screen elements and key actors:
Actor role is by pill color
Role in the SDLC is captured by the capsule color:
- Gray: Customer
- Dark Blue: Requirements manager (dev team)
- Yellow: Product owner
- Green: Developer (dev team)
- Light blue: tester (Dev Test)
- Gray: Customer
- Dark Blue: Requirements manager (dev team)
- Yellow: Product owner
- Green: Developer (dev team)
- Light blue: tester (Dev Test)
Artifacts (items that are processed in this simulation):
- Defined Requirement
- Tasking (JIRA entry)
- Implementation
- Testing (deployable)
- Defined Requirement
- Tasking (JIRA entry)
- Implementation
- Testing (deployable)
The following explains the simulation:
GOAP in action for the Software Development Life Cycle (SDLC)
References:
FEAR and GOAP: https://www.gamedeveloper.com/design/building-the-ai-of-f-e-a-r-with-goal-oriented-action-planning
Unity GOAP: https://youtu.be/Q7aHXn_LypI?si=Tr0_55fSG766ov5X
